Skip to content

Fix: Add missing uv installation to deploy workflow#934

Merged
SaboniAmine merged 4 commits into
masterfrom
copilot/fix-c73aba9c-79b1-4b56-a08f-86730c0693b2
Sep 24, 2025
Merged

Fix: Add missing uv installation to deploy workflow#934
SaboniAmine merged 4 commits into
masterfrom
copilot/fix-c73aba9c-79b1-4b56-a08f-86730c0693b2

Conversation

Copilot AI commented Sep 20, 2025

Copy link
Copy Markdown
Contributor

Problem

The production deployment GitHub Actions job was failing at the 'Deploy backend to Clever Cloud (PROD)' step with the following error:

uv: command not found

This occurred when trying to execute:

uv pip compile carbonserver/pyproject.toml > requirements/requirements-api.txt

Root Cause

The deploy workflow (.github/workflows/deploy.yml) was missing the uv tool installation, while other workflows in the repository already properly install it using the astral-sh/setup-uv action.

Solution

Added the missing uv installation steps to the deploy workflow:

  1. Install uv using astral-sh/setup-uv@caf0cab7a618c569241d31dcd442f54681755d39 # v3.2.4
  2. Set up Python using uv python install 3.12

Both steps are positioned before the deployment step that requires uv, ensuring the tool is available when needed.

Changes

  • Added 2 new workflow steps following the exact same pattern used in other workflows (package.yml, test-package.yml, build-server.yml)
  • Used the same action version for consistency across the repository
  • No changes to deployment logic or functionality

This is a minimal, surgical fix that resolves the immediate deployment failure without affecting any other aspects of the workflow.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • astral.sh
    • Triggering command: curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

This pull request was created as a result of the following prompt from Copilot chat.

The GitHub Actions job for the production deployment is failing at the 'Deploy backend to Clever Cloud (PROD)' step because the command 'uv pip compile carbonserver/pyproject.toml > requirements/requirements-api.txt' results in a 'uv: command not found' error. This indicates that the 'uv' tool is missing from the runner environment. To resolve this, update the workflow to install 'uv' before this step. Reference: image1


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: benoit-cty <6603048+benoit-cty@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix workflow: Install 'uv' before backend deployment to Clever Cloud Fix: Add missing uv installation to deploy workflow Sep 20, 2025
Copilot AI requested a review from benoit-cty September 20, 2025 18:21
@benoit-cty benoit-cty marked this pull request as ready for review September 22, 2025 07:14

@inimaz inimaz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Can we launch this before merging to try?

@SaboniAmine SaboniAmine force-pushed the copilot/fix-c73aba9c-79b1-4b56-a08f-86730c0693b2 branch from 9b0c678 to 9d1a9d8 Compare September 24, 2025 17:11
@SaboniAmine SaboniAmine force-pushed the copilot/fix-c73aba9c-79b1-4b56-a08f-86730c0693b2 branch from 9d1a9d8 to 5f38afd Compare September 24, 2025 17:19

@SaboniAmine SaboniAmine left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@SaboniAmine SaboniAmine merged commit 987997c into master Sep 24, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants